в приложениии используется Stateful bean, при первом заказе(в текущей HttpSession) создается SFSB через JNDI и кладется в HttpSession, при уничтожении сессии - висит HttpSessionListener, вызывается метод @Remove у SFSB, + он удаляется из HttpSession руками, иногда , до окончании HttpSession, при обращении к SFSB вылетает javax.ejb.NoSuchObjectLocalException
это и не понятно,
спасибо

разве контейнер может сам безвозвратно уничтожить SFSB ?
в ejb3 in action расписан такой lifecycle;

However, you should note that we
invoke the very same method for both the PreDestroy and PrePassivate callbacks:
@PrePassivate
@PreDestroy
public void cleanup() {
...
}
Similarly, the exact same action is taken for both the PostConstruct and Post-
Activate callbacks:
@PostConstruct
@PostActivate
public void openConnection() {
...
}
To see why this is the case, let’s discuss activation and passivation in a little
more detail.
Passivation and activation
If clients don’t invoke a bean for a long enough time, it is not a good idea to continue
keeping it in memory. For a large number of beans, this could easily make
the machine run out of memory. The container employs the technique of passivation
to save memory when possible.

Passivation essentially means saving a bean instance into disk instead of
holding it in memory. The container accomplishes this task by serializing
the entire bean instance and moving it into permanent storage like
a file or the database. Activation is the opposite of passivation and is
done when the bean instance is needed again. The container activates
a bean instance by retrieving it from permanent storage, deserializing
it, and moving it back into memory. This means that all bean instance
variables that you care about and should be saved into permanent storage
must either be a Java primitive or implement the java.io. Serializable
interface.

Destroying a stateful session bean
Calling business methods marked with the
@Remove annotation signifies a desire by the client to end the session. As a result,
invoking these methods triggers immediate bean destruction.

до окончании HttpSession или без явного logout юзера, ни один метод с @Remove не вызывается, то есть бин должен десериализоваться обратно в винта, или я не понимаю чего то

возможно вот оно

возможно вот оно,
http://docs.oracle.com/javaee/6/api/javax/ejb/StatefulTimeout.html
книги не успевают