OTS11 — ORB / client interceptor behaviour on location forwarded IORs

With respect to the OTS changes introduced by the Messaging spec,

In the case of persistent servers, the IOR will point to a Activation Service. When the client
invokes the IOR the Activation service would in turn return a location forwarded IOR, which will
point to the actual servant.

Assuming that client has an active transaction and the client interceptor checks as specified by the
Messaging spec are performed when the original IOR (which points to the Activation Service) was
invoked, the interceptor hook would throw a INVALID_TRANSACTION.

Thus the client side interceptor checks would not allow location forwarding at all to happen. So,
the bigger question is : is it possible to remove client side checks, and propagate the transaction
context unconditionally ?