exception in destroy method results in "javax.ejb.EJBNoSuchObjectException: Could not find Stateful bean"

This affects JBoss 4.0.5.

When a system exception occurs in a @Destroy method of a SFSB, the bean gets removed (because of the @Destroy annotation), then the container tries to remove it a second time (because of the exception), and this results in the swallowing of the original exception, with an EJBNoSuchObjectException taking its place.

Solution: the interceptor that handles the @Destroy annotation should not try to remove the SFSB when the destroy method throws an exception.