I'm not entirely sure if this is the best language to program this specific program.

You mention "best", but which measurement are you using? Best speed wise? (Nope, don't use Perl). Best memory usage? (Nope, don't use Perl). Runs on all the important platforms? (Nope, don't use Perl). Has the most coders available on the jobmarket? (Nope, don't use Perl) Has the best type checking at compile time? (Nope, don't use Perl) Uses as little "line noise" as possible? (Nope, don't use Perl) Went through a standardization process? (Nope, don't use Perl) Is never the butt of Internet jokes? (Nope, don't use Perl) Is used by all the cool kids? (Nope, don't use Perl) Comes with a GUI build in the language? (Nope, don't use Perl) Is a child of the 21st century? (Nope, don't use Perl) Doesn't show UNIX heritage? (Nope, don't use Perl) Has Unicode support that just works? (Nope, don't use Perl) Has threads build in, instead of bolted on? (Nope, don't use Perl) Everything is an object? (Nope, don't use Perl)

Frankly, I cannot give you any reason why you should use Perl. But if Perl suits your mind set, by all means, use it.

It most definitely isn't the-machine-that-goes-ping Java, still deeply rooted in the 1980's. Not speaking about the fact that quite a few requirements are either nonsensical or ill defined.
"Best speed wise?" Which speed? Development or runtime? And keep in mind that in both cases it depends a lot on the task and the developer(s).
"Runs on all the important platforms?" Important to whom? And what are actually the platforms Perl doesn't run on? Some smartphones?
"Uses as little "line noise" as possible?" Yes, we all know that "ASSIGN FIVE TIMES AVERAGE_SALLARY TO MAXIMAL_MANAGERS_SALARY" is preferable.
"Comes with a GUI build in the language?" Beg your pardon? I guess you do not mean a GUI for the developer, right? Because that's not the matter of a language, but rather its implementation, besides there are several GUIs for Perl development. On the other hand you can't mean GUI as a library to create graphical applications because ... frankly that's a matter of libraries and most, if not all, languages have several of those. Which a Java fan should be well aware of thanks to the mess of Java GUI libraries. So what is it you meant?
"Everything is an object?" I never understood why would that be a good thing, but then ... there's no pleasing the OO purists.