IIRC, this type of problem is also happens with $0 in simple shell scripts. On some systems $0 is just the base file name, in others it's an absolute path to the script.

FYI, you can get the thing to work if you use the full path to the perl:

$ type perl
perl is /usr/local/test/perl/bin/perl
$ perl -e 'print "$^X\n"'
perl
$ /usr/local/test/perl/bin/perl -e 'print "$^X\n"'
/usr/local/test/perl/bin/perl
[download]

So a shell script wrapper might also be a workaround, to set up an environment where the full path is used.

More to the point, is there a fix for this, yet?

Thanks, Bob