My immediate reaction is to cringe, and then the next thought is the absolute URI should be used as it isn't ambiguous.
I can't think of anywhere in the specification which specifically talks against this pattern, but it seems to go against everything I know about hypermedia. As /api/users/me will never be consistent across users, as it is utilizing request state to respond.
I think a much MUCH better solution would be to implement this as a filter parameter, and broadcast this as a link of some sort, something akin to:
Implemented however your filtering strategy allows, this wouldn't violate the intent of the spec nor the definition itself.
I still find this solution less than ideal, as the client should get this information at the same time it receives it's authentication token. The responsibility to keep track of this information should fall on the client, if it's being stored in a cookie or localstorage it should stay there for access.
Anyway, I'm done bikeshedding on this for now. Good luck.