Enitity bean calls remove(Object object) method on entity bean, then the bean is deleted.
Normally, it is your client codes that invokes the remove(Object pk) method rather than another entity bean. Remember, an entity bean is a noun. It represents something rather than do something (verb - session beans). If you're thinking of the parent-child (CMR) kind of relationship, you'd be using cascade delete in the DD instead.
What happens when two EJBObjects (EJBObject_1 and EJBObject_2) are representing a single row say #10-Valentin Crettaz
Now EJBObject_1 gets a call to remove #10 and that too it is in transaction. What will be the containers approach.
When the client invokes a method from the component interface of a bean that had been removed, an exception will be thrown. Thats the way containers inform the client that the bean is no longer there.