You keep executing the function because it's on the stack. The program counter keeps moving through the method until it hits a return statement. God help you

You keep executing the function because it's on the stack. The program counter keeps moving through the method until it hits a return statement. God help you if you try to reference one of the class' internal data objects as their heap space could have been allocated to something else running on another thread.