Cascading node_delete()s do not work

I am witnessing that node_delete() cannot perform cascading deletes.

Let's say I have two custom content types A and B

In the implementation of A_delete(), at some location in the middle it calls node_delete(b*) and b* is an instance of B.

If I call node_delete(a*) and a* is an instance of A, then as expected A_delete() is called.

As explained previously, during the deletion process of A node instance it gets to location where it call node_delete(b*).

What happens next is that B_delete() is called and completed, but A_delete() does NOT complete. In other words, A_delete() does not continue its deletion process after calling node_delete(b*).

Is this an expected behavior?