A little difficult to comment on without some pretty specific information.

As a general rule we should only declare globals with considerable malice of forethought. Why do you need a global? Why not some other scope?

I have never tried a 'require' in a mod_perl process, but again, why do a require? Why not contemplate loading a config file in some established format into a local data structure as needed, and freed when done?

As to actual memory leaks? Well, even though perl_mod processes are persistent they are not infinitely persistent - they don't last for ever. You really should do some benchmarking specific to your own situation. I would also advocate that you join one of the mod_perl lists at apache.org and ask these questions there as well, there are plenty of very experienced folk there that may not see your question here.

jdtoronto