I am not sure what you want to know. Stateful Session Beans maintain state in memory and persist to some form of storage if the EJB Container passivates it. That is why all state in a Stateful Session Bean must be Serializable.
before you call method of EJB, you must have the instance which implements remote/local interface. then you call the method again, using the same instance, so that the EJB is still the original one(at least, looks like the same one. container may have mechanism to share EJBs). the reference of instance may be kept in web tier session if we talk about web application.
The airline is called "Virgin"? Don't you want a plane to go all the way? This tiny ad will go all the way:
Free, earth friendly heat - from the CodeRanch trailboss