PAR is very cool, but I've had problems using it with more complex dependency chains -- i.e., modules using PerlTk, or if the perl on the compiling box uses shared libraries and the target box doesn't have the shared libraries. That's perhaps not surprising.

Would suggest that the monk first try PAR, yes, but if he really needs an executable and PAR doesn't work, ActiveState does make a fine product...