I agree that the most potential for growth lays in the managment side. Most perl developers already know how great it is. It's convincing managment that it's the way to go that the trouble comes.
I don't know how many times I've heard from managment that they want java, everyone is using java. They hear platform independence and they say wow, I can develop this on a windows box and then not have to worry about where I'm going to host it, not knowing that the same can be done with perl for the most part. Management tends to follow the hype, believing that if everyone else is doing it, I can't be wrong. They are driven by money, but follow the hype to preserve their reputation.
Maybe this is what needs to be done with perl in the managment communities? I think it may be hard to get the same kind of marketing budget as sun though. So, maybe it's up to the developers to convince managment by showing them what can be done with perl. I think anyone in group B.1 and above should take on some of the responsibility of convincing managment that perl makes sense. Starting with group B.2 because they should be easier converts.
I'd like to hear what people think of this.

1. perl 5.004_04 - 5.005_3
2. Debian 2.1 and Debian Potato
3. Haven't had a chance to get to 5.6 yet, except on a windows platform, but haven't played with that much