IMO the real question is what such EPRs may be used for. If they planned as replacements for URLs and *full* such EPR is going to be put into every SOAP header then I would vote strongly against. But if such EPR is just a way to describe service (same as corresponding section in Glue document) and are ony meant to be used in some kind of information system/port then why not.

EPRs don't go in SOAP headers. (Somehow there is a common misconception that they might.)

You are correct in your latter statement: an EPR is a "far-pointer" to a resource endpoint and contains the information that a client needs to know in order to establish communication with that endpoint.