But you are correct--it is far from the only example. There are major problems with iOS's model, too--once your device has received its last update, you're stuck with its rendering engine forever! Browsers using alternate rendering engines aren't allowed in the store. With Gingerbread, at least people can install a browser with a newer rendering engine.
But in general, I think the "Gingerbread is the new IE6" claims are pretty hyperbolic. IE6 remained such a scourge because so many companies wouldn't upgrade it to maintain consistency and compatibility with their custom, non-standards-compliant internal web applications. In contrast, mobile devices currently aren't kept very long, and there's quick iteration. After a few years, those Gingerbread users still using their devices can get a new browser if they're insistent on using the device, and idevice users will have to get a new idevice. But those users won't be tied to using those devices by corporate policy. At worst, I think developers will have to worry about the Gingerbread browser and older versions of mobile Safari for a few years, not the better part of a decade like with IE6.
[1] https://developer.android.com/about/dashboards/index.html
I haven't used iOS enough to say for sure, but isn't Mobile Safari also tied to the OS version in a similar way and can't get updates without the OS being updated?