To expand a bit on the somewhat terse reply by Anonymous Monk, you will have to show more conclusively that it actually is Starman that has a memory leak.

The easiest way to do that is to strip down your application to the bare minimum application that runs and still exposes the memory leak in Starman. Most likely, while stripping down your application, you will find out that somewhere in your application you are creating memory cycles that cannot be relased using the reference counting memory management that Perl uses.