This probably just crept up on everyone
Knowing programmers as I do they won't necessarily think 'big picture', they'll just transfer data at regular intervale because its something they know how to do. They won't think about the mechanics of a protocol -- the actual data transferred is just the tip of the iceberg -- or about the cost because when they developed this code it just wasn't a parameter that was part of the specification.
Now they're aware they might be a bit more parsimonious, especailly if there's a lawsuit to get their attention. They really aren't the only offender; they might be the sloopiest but bandwidth usage -- and hogging -- is endemic, its a blight on applications development. It also offers a potential 'in' for an Andriod alternative; currently everyone uses Goggle's software stack because its convenient and everyone else is doing it (ignore Apple for the moment). If some event occurs that forces a substantial part of the user base away from Andriod then there's plenty of scope for the new operating system to tidy up, not only saving users money but also making much more effective use of mobile bandwidth, something that's a big selling point in many places where bandwiidth is either not easy to come by or expensive.