I understand how you can come to this conclusion but that just isn't how things work when it comes to dropping product support. Businesses scope out far ahead of time the potential business loss/gain when it comes to supporting new technology or dropping a legacy platform. You're looking at it from the perspective of telemetry from short-term gains. There's also potential long-term gain/loss (i.e. legacy owners who buy the product a year or more down the road).
However let's get off the financial aspect. The decision to drop legacy support is not an at-whim process that one or two people make while staring at financial reports. Here's a list of reasons why you would drop product support:
1. Company A did not renew a contract license for 3rd party software use with Company B.
2. Company A is violation of a contract agreement by continuing to use 3rd party software created by Company B.
3. Company A can no longer support the product because Company B who owns the product officially dropped support and/or announced EOL.
4. Company A can no longer support the product because Company B went out of business/bought out.
5. Internally the development team has switched over to a new technology that is not compatible with legacy products.
6. Not enough staff to support both a legacy and nextgen team.
7. The number of clients using legacy has fallen into niche/one-off status (i.e. 5% or so of your entire customer base).
8. Incompetence.
Let's translate these into something you might understand. At the time when Windows XP was the minimal supported client OS, I was also responsible for product testing Vista, 7, Svr2003 all ed, Svr2008 all ed, 2011 SBS, Office XP/2003/2010, IE 6/7/8/9, Safari/Chrome/FF/Opera, Adobe products, licensing for all those listed, and finally the hardware used for testing and certifying all those listed. I tried unsuccessfully for two years straight to have XP dropped as a supported product. The reasons why were because supporting XP held back our ability to focus on 64bit improvements and doubled my testing time since I had to support all products that were XP-compatible. However if I had unilateral decision to drop it, then it would've impacted millions of our users who refused or could not afford to upgrade. Once a year I had to write up a review when our new-year release was coming out. Each year I'd write a request to drop support. My review had to go thru my team which included other devs who made a decision. The opinion/decision would pass on to product management. They would talk with the Integration team that included experts from other applications, the Lab, and the Support staff. Their opinion/decision went on to Finance, Marketing, Publication and the Executive teams. A month if not more down the road I'd get a 'yea or nay' on my proposal plus feedback.
In the 3 years it took to finally get XP dropped, our company had rolled out with a brand-new application versions that didn't include XP-compatible technology. So that spread my testing compliance out even further since I had to "cut corners" on legacy testing to confirm the new versions were being thoroughly reviewed. I also had to spend time making small code changes for our legacy version since it was in maintenance mode. The legacy apps had to have the same features as the nextgen, less the exclusive 64bit and non-XP enhancements. We disclosed the features, their differences and the system requirements on our website (something I was also responsible for). There are checks and balances throughout the entire process. I wasn't allowed to publish anything, enforce decisions, or accept new technology changes that wasn't reviewed by my immediate supervisor, their boss and at least two other impacted teams.
What in the world does that have to do with PS3 and XBox360? The same business principles apply here. Can you imagine if I and a few rogue developers got our way and decided to say "Eff XP users. Upgrade your ish." There would've been bad reviews and pink slips being issued out. Can you imagine if we pulled support for XP mid-year that impacted millions of client users without giving them prior notice? Can you imagine the fallout if they found we planned to pull support but didn't tell them prior to selling them the newest year release? We get a ton of angry complaints, clients going over to competitors, and refund requests. I'd rather sit on a escalated support call and hash it out with IT manager who's a bit more understanding than someone from a client's Purchase team.
Something you have to understand is that support is included in the cost of purchase. What level of support you get is done at the point of sales. That means the company selling the product absorbs the cost of support (or rather passes on the cost in ticket price) for the length of time they express and the type given (free, cost per call/transaction, liability). If you state that you're going to offer technical and application support for X amount of time, then that also includes changes that go along with it. What BW or EA decided to do was pull a grey area tactic on legacy gamers. The decision to drop DLC support for legacy platforms was made before Nov 2014. I almost guarantee it. I don't see how they didn't see it coming. Had they advertised that they'd discontinue DLC support for legacy consoles mid-year then obviously legacy gamers wouldn't buy the game, at least quite enough that it would effect their bottom dollar. R* did the exact same thing except R*'s people are smarter. They called the new DLCs "XBone/PS4 exclusives for GTAV". If you read the R* forum you'll notice that it took gamers a couple of months to realize they got snowjobbed.
I don't begrudge BW/EA for dropping support for legacy platforms, but at least have the balls to be honest about it. The reason I called the practice unethical as opposed to illegal is because there is no specific law or EULA violation I could find to say what they did wasn't on the up-and-up. That's one of the problems I expressed about game publisher accountability. It's free market and it's like the wild, wild west. They can make up the rules as they go as long as there is noone or a governing body to challenge what they're doing.