Big enterprise, wants predictable recipes for things, not the wild hubris that Perl allows. They want employees trained in a system that allows for the employees to be disposable such that replacements can step right in and understand the objects.

Quite right. Which reminds me of one more thing: they want languages which play nice with CASE tools — both for reverse engineering (deducing object models from source code) and for "forward engineering" (generating source code from models). Java is great for this; Perl, not so much. :-)

... object models that reflect their company, which are compatible with other company's models ( makes buyouts and mergers easier) ...

Interesting hypothesis, but I think rather too optimistic. In my experience, companies tend quite the opposite way: every one wants to invent their own models; even when another company's models might be demonstrably better, the "not invented here" mentality almost always rules. I see this a lot, especially in the government sector.