(this seems to be the case in a low percentage of views, say one in ten)

Let me guess... you start 10 server processes... right?

Try starting just a single server and see if that doesn't raise your 1 in 10 to a hundred percent. ;-)

I think you should certainly be doing this another way (say, encapsulating the data in an object rather than using a package's whole namespace, for instance.) But, I understand you are already entrenched and trying to make a go of what you currently have... Still, I'd consider some sweeping changes for the next revision.

-sauoq
"My two cents aren't worth a dime.";

In the light of the further info, my suggestion does help at all.

Given the status quo, sauoq's suggestion of Symbol::delete_package (used as early as possible) seems about the best your going to get without pretty fundemental changes to your app architecture.

I keep wondering if you couldn't rename the uniform package statements to use some sort of hierarchal naming convention and then use that to restrict what information the user sees according to their group rights, but that sort of change is probably so extensive, that you would be better off rewriting from scratch to use a better architecture.