InfinitePool maintains a list of all objects that have been created and not yet removed. For SFSBs this essentially functions as a second cache and makes passivation pointless, since passivating from the SFSB cache doesn't remove the ref in the InfinitePool.

The issue is resolved for AS5 with https://jira.jboss.org/jira/browse/EJBTHREE-1367, however backporting to EAP 4.3 the changes for this JIRA and the changes that 1367 depends on is not really an option.

https://jira.jboss.org/jira/browse/JBPAPP-1201 ensured the EJB was removed from the pool when it is destroyed, but doesn't address the passivation issue.