It's far easily to clearly detect a Perl bug if it's demonstrated in 5 lines of code, rather than buried somewhere in the middle of a 500-line program. It's always worth getting someone else to look it over and confirm that this really is a Perl bug, not just a thinko. If there's nobody around to do that, consider asking on the comp.lang.perl.misc or comp.lang.perl.moderated newsgroups. Follow the list for a few weeks or months to get an idea of what goes on, and see if anything pops up that you're interested in. There's certainly a place for anyone who truly wants to get involved, and over time, you'll find it.
Patches speak louder than words.
Having ideas is good, but taking the time to implement them will improve their credibility. At least one person will think your patch sucks. It's better to let the code stand on its own merits than get into arguments. I'd like someone to check it over before I post it to the list. We don't bite, and we appreciate people who want to help.