I don’t know much about the page protection features of Seam Faces, so I’m only guessing here. But I think the problem is that PrettyFaces internally forwards requests to the correct JSF viewId if a request to the REST URL is detected. So Seam Faces only sees the JSF view id and doesn’t know anything about the original REST URL. So of cause Seam Faces is redirecting to the view id.
I don’t know how the Seam Faces page protection stuff is implemented. If there is something happening in a servlet filter, you could try to change the order of the PrettyFilter and this filter.
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.