Some people shy away from highly convenient Perl5 modules because they sometime deal with objects. And while the managers haven't figured it out yet, the programmers realize that objects are too often used to make something overly complicated without providing much realistic increased usefulness. On the other hand, some problems very much lend themselves to objects. This scares people. There's a tremendous difference between merely knowing enough OO programming enough to merely use someone else's modules versus enough to actually design and implement one yourself.
People are afraid of the having to be the latter just to get at the former.
This is far from the case. There isn't much to using an object module. If you haven't used perl5 before, you just need to brush up on at most one or two new concepts that you wouldn't have seen before. The statement require Module also loads it, but only at run time, and doesn't do any imports. You might think of it as sending a message to that object.