The CORBA Component Model has finally clarified the semantics of locality
constrained objects.  My understanding is that the objects do *not*
require a Servant, and are directly implemented by the proxy.  In fact,
a locality constrained object is only accessible as long as there is
an object reference for it.
This is related to the library footprint because currently TAO implements
locality constrained objects using separate servants and object references,
reducing the number of classes would reduce the code size.  It will also
reduce coupling in the library, as clients would not need to link the servant
base code (and carry a good chunk of the POA with them).