The entity Bean Provider can use the ejbRemove method to implement any actions that must be done before the entity object�s persistent representation is removed. The container synchronizes the instance�s state before it invokes the ejbRemove method. This means that the state of the instance at the beginning of the ejbRemove method is the same as it would be at the beginning of a business method.
If not, the bean provider would not know the exact state of the entity. sounds reasonable?