Home objects can be held as long as you want
to after looking them up from JNDI as they do
not go "stall". Of course if the container goes
belly up, you are stuffed and get a remote exception
when calling create()...
This is a regular practice for me. If I need a
stateless session bean, I obtain the Home and create()
the remote once, up front. If it is a Stateful bean
that I need I obtain the Home once and create() the
remote on demand.
You can certainly obtain the Home object for an
Entity and hold on to that.
Technically, Home and Remote objects can be
serialised by a (Java) client to a persistant store
and "reconstituted" later.
Hope that helps.
Do you mean that container restart invalidates all my home (not even mentioning the remote) interfaces?