The associated forum posting indicates that the check for calling getEJBObject from ejbPassivate is incorrectly setting the caller's state to be that of an IN_EJB_HOME method. It's really a home method invocation of another bean that is causing passivation to occur.