Definitely Scala (Score 1)

If you've got Java and C++, presuming you're fully using the power of these languages, then you should move to Scala. Not to slam any language but in terms of experience if you've only programmed in PHP you'll find Scala "complex". A Java programmer will find Scala complex at first and absolutely wonderful as it soaks in. A C++ programmer already has enough grasp of language subtleties that Scala will not be a problem.

My take on it is it is a sophisticated tool for sophisticated applications, having levels of richness and expressiveness that I haven't experienced in years... got the same feeling as when I moved from C++ to Java when it was new.

I've been using it for about 6 months having written 1000s of lines of code now. Absolutely loving it--and even though I was happy working in Java, I wouldn't go back. (The longer I use Scala the madder I get at Java--why aren't some of the low-hanging language features in Java by now? For Java7 they're talking about strings in switch statements and I'm supposed to be impressed, like they're doing me some great favor?)

Scala-to-Java interoperability is fine... not quite as seamless as the glossy brochure leads you to believe but not at all bad. I've written EJB web apps in a mix of Scala and Java, utilizing a number of 3rd party libraries in both languages. No issues. Actually the only issue I had was with Scala's actors I was trying to use in an EJB. Since actors are basically fancy threads and you're not supposed to create threads in an EJB, I got the trouble I deserved. Actors outside the EJB container work great.

It's a risk--few enterprises are aware of, or ready for, Scala (or other "alternate" languages for that matter), but think about it and it seems inevitable that Scala will capture some enterprise share due to its Java interoperability and strong typing (I love loosely typed script languages too, but I wouldn't want a 50K-line enterprise app done in one).