Generally, I think you should never choose a technology because of its perceived value on the current job market. You should choose technologies because there's something good about them and you can do great stuff using them. To be able to judge that, you probably should know a few, though.
Also, you don't really switch tech, you just add new ones to your repertoire. If you learn Java now, you can still code PHP, right? My guess would be, that you even write better PHP by learning something else. Not because of PHP in particular, just because knowing more different paradigms helps you understand each one better.
They say the second programming language is the hardest to learn, because it's the first time you have to really grok the difference between language-specific issues (such as typing) vs. API/library-specific (such as the concepts behind a particular framework) and general programming issues (such as big-O). Past that hurdle, it becomes more fun all the time, I think.
My first serious switch (I had toyed around with Python before) was from PHP to Java, and it was quite an eye-opener (and I didn't like the switch at all for quite a while). For the past two years, I'm constantly switching from Java to EcmaScript (both JS and AS), and for me, that was really, really instructive. I had read books about LISP and even played around with it a little, but it wasn't until I actually worked in JavaScript, that I realized what the strengths of this sort of language are.