There are, essentially, two options open to you to solve your issues.

1. Don't use strict. This is generally considered poor programming practice for projects you want to have run more than once. However, strict wasn't in Perl 1.0 and large projects were still done.
2. Rewrite what you're doing.

The issue is this - to make (what I know) of your project to work under strict, you will seriously cry. In fact, it would take longer to shoehorn strict into your design than it would to rewrite your project to work with strict. A few possible rewrite directions:

1. Consolidate all the globals into a hash and declare that hash with our or use vars.
2. Consolidate everything into a Singleton.
3. Restructure your project so that it doesn't use globals at all.

That last sounds really hard, but it's just a small shift in your thinking at the base level. Once you make that shift, you'll find it much easier to work with your code because you KNOW exactly what's happening at any given spot. *shrugs* YMMV

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.