QA is usually not the problem, its either the amount of resources/time QA is allowed to spend on a project or the producer not prioritising the right bugs to be fixed.
Testing is just the end part in a process, QA should encompass the entire process. If all the other phases in a project do not take into account QA best practice then this is why these kind of things often happen but QA gets it in the neck. Its surprising but allot of companies resist this sort of approach mainly because developers object to it or its seen as costly.
Duke, the reason why Dice doesn't do that is because EA has a certification phase which takes a while to pass and it all has to be booked into EA QA so they do it in batches. If Dice were there own publisher to they could use a method called Continuous Integration which would allow them to roll out fixes pretty fast. EA is just to big and complicated for them to react quickly enough to fixing small bugs.
I can also see why they don't want to develop for PC much longer, it requires enormous man power to test the functionality of a title then do the compatibility which is the same thing again but 10 fold. Its not something you can automate much of so you need allot of manual testers, which is extremely expensive. Even on consoles now, its not as easy as it once was to test a game (or any software, principles are the same).
I can say all that from being associated QA manager and QA manager on several triple A titles over the years.