As an adjunct, I don't got no choice in the language. The "Advisory Committee" wants Java. Back in the Dark Ages, CS was taught in FORTRAN, than it moved to C, then Pascal to Modula, then C++, now Java or C#. Next semester, I get my way and my classes use Python.
Frankly, I don't care about the language. Understand the fundamentals, and the reference manual is your best friend. There are some classes where the language is critical and often specifi ... operating systems - is always C. Database is always SQL for relational (unless it's grad school where you have to write one from scratch, so it's C again) or one of the NoSQLs. Computer graphics...back to C. Anything that's high performance or number crunching, it's C/C++. Personally, I'd teach everything in ARM or Motorola 68000 assembly. Just to be annoying.
But Android is a Java platform, and we see more requests for mobile development, so there's lots of Java.
What's interesting is that younger faculty ( newish PhDs ) are limited in languages. They know the theory and generalities of a few languages, but none of the nuances such as issues with versions. At my school, most of the older faculty have extensive industry experience and have gone thru the agony of versions, legacy systems, and are fairly fluent or can at least get by, in a dozen or so languages.
I keep telling my students, you really learn a language when your paycheck depends on it.