EJBLocalObject in a Clustered environment.
Let's assume that we have a huge project developing a J2EE app. We make lots of use of EJBLocalObjects well aware that the servlets and EJB's will execute in the same JVM. At some point in time, we decide to deploy our app in a cluster that supports HTTP session failover.
The fact that servlets and EJB's run in the same process will still be true. We never make interprocess calls to our EJB's. My concern is, if I have a EJBLocalObject stored in my HTTP session, what will happen when that session is serialized and deserialized? Is the reference between this object and the EJB container reestablished? Does the J2EE standard enforce this in any way?

