however for entity beans, ejbRemove will actually remove it from the database. so in this case, you need two calls one to take the bean back to the pool and one to actually destroy it. so we have two different methods.

for session beans, its all the same coz there is no actual destruction involved. so I guess its oj there is only method.

once someone understands the fundamental differences between session and entity beans, i think they can see why ejbRemove behaves differently for each of them.