TRANS13 — is org.omg.CosTransaction.Current object locality constrained ?

The latest Transaction Service (00-06-28.pdf) specification reads:

"The Current interface is designed to be supported by a pseudo
object whose behavior depends upon and may alter the transaction
context associated with the invoking thread. It may be shared with
other object services (e.g., security) and is obtained by using a
resolve initial references(TransactionCurrent ) operation on the
CORBA::ORB interface. Current supports the following operations: ..."

Does the above imply that the Current object is not locality-constrained and could be exported to
other processes ? If so, this seems to contradict the CORBA Core Section 4.8 which makes a blanket
statement about all Current objects being locality constained.

see below