max-bean-life specifies the maximum period of inactivity, that a bean can exist before being removed from the store.
It seems, that ejbRemove is not executed in this case. This may be understandable, but I think it would be better, if ejbRemove or another method would be executed at this moment. Perhaps it should be possible to add code to the remover?
What do you think about this problem?
After further thought about the problem I think, that the remover should avtivate the bean and then invocate the remove method.