Actually, I think that goto will clean up the stack. My "evidence" for this is:

#! perl -slw
use strict;

sub a{
    my( @args ) = @_;
    goto MAIN unless @args;
    a( @args[ 100 .. $#args ] );
    return 1;
}


printf 'Check ram'; <STDIN>;

a( 1 .. 10000 );
MAIN:
printf 'Check ram'; <STDIN>;

my @a = ( 1 .. 50000 );
printf 'Check ram'; <STDIN>;
[download]

At the second ram check, there has been substantial growth in the process memory (as expected) through the 100 or so chunks of ram littering the stack.

But allocating a new large array after the goto shows barely any increase. That's leads me to think that the statement in perlsub on goto's "It can be used to go almost anywhere else within the dynamic scope, including out of subroutines," means that the stack is cleaned up.

Whether it's the Right Way for your application is a different matter. The last para of the same section says:

In almost all cases like this, it's usually a far, far better idea to use the structured control flow mechanisms of next, last, or redo instead of resorting to a goto. For certain applications, the catch and throw pair of eval{} and die() for exception processing can also be a prudent approach.