Removing session bean twice - strange effects in JBoss

[Alex Molochnikov]

My code erroneously sent remove() call to a stateful session bean's remote
interface twice. The first call triggered ejbRemove() method on the bean,
but the second call (to an already removed bean) sent it into a new creation
cycle, calling setSessionContext() method (and the stack trace shows create
methods from the container).

Should it not have thrown an exception instead? Did anyone experience
something like this? I am running JBoss 4.0.1 SP1 on Win XP Pro under Java
1.5.0-04.

Alex Molochnikov
Gestalt Corporation