|What's the point of mastering 15-year old technology? Do you plan to travel back in time?|
If you're learning C++ at home for a hobby, then, no, there's no point.
But I can tell you that in industry, there are a lot of companies who haven't yet migrated to development environments that support C++11. Companies often have ongoing projects that have been around for years, and will stick to operating systems, compilers and so on that have been thoroughly validated and approved by their procedures. Individuals are not at liberty to simply switch to newer versions of the OS or compiler, and must work using the approved tools.
The process of validating and approving newer versions can be time-consuming and expensive, and the developers will usually have a ton of other work to be getting on with. Many developers - and managers - will work under a principle of "if it ain't broke, don't fix it. When a company's success depends on producing work in a timely fashion, I can't say I really blame them.
Additionally, many companies will have a set of established coding guidelines and practices. C++98 has been around for a long time, and commonly-understood ideas of "good practice" are widespread and mature. With the features of the new standard, this is less well-understood, and many companies will be reluctant to make the change to C++11 without first being confident they can specify good guidelines for the developers.
In short, then - if you want to work as a professional C++ developer, there's a very good chance you'll be working in an environment where you can't use C++11 features. So it will set you in good stead to learn how to program well, and implement the behaviour you want to implement, without using C++11 features.