I hate StudlyCaps too, so I always name modules with single words. Nouns, typically.

In object oriented terms, I have found that if I need an adjective to describe a classname, then there's probably some inheritance of more fundamental features.

For example, say I want an interactive widget. Thinking about it, I realize that the adjective clues me in on the possibility of other kinds of widgets. I may or may not be better served with a separate namespace like Widget::Inert and Widget::Interactive under the more general Widget namespace and class. But I very rarely would use a name like InteractiveWidget which just looks BuTtTuGly to me.

One thing to keep in mind: if you're using a lot of other people's modules from CPAN, then you're going to have to accept the names they already have, so you might as well become disabused of your notions of avoiding all StudlyCaps entirely.