I'm pretty sure that this is not needed because you can't return to the source of a goto

Indeed, goto &foo pops the current call frame and replaces it with a new frame, rather than just pushing an additional one as a normal sub call would do. The following consumes lots of CPU but uses constant memory:

sub foo { goto &foo };
foo();
[download]

Dave.