People have stuck with XP until MS stopped supporting it.
About half the clients I work with still are running XP, and most will not change until they HAVE too....support or no from MS.
I suspect the same will be true for 7 - a fair number of companies build process flow around a working model, and are unwilling to disrupt production or incur substantial cost to "repair" a working system, no matter how often MS puts out an updated OS.....
I find this approach to be sensible - it's that whole "If it ain't broken...." routine. To be sure - I see this most often in a manufacturing setting, where a computer has been integrated into the actual manufacturing process (CNC for example) or where a complex system of reporting and accountability are in place using legacy hardware - sure you can update hard and software, but there are considerable costs involved in redesigning the process flow, retraining workers - and the concordant loss of productivity and decline in manufacturing output while the system is installed, configured, and troubleshooting in addition to training personnel makes it a major investment....
I find the same dynamic to be true when it comes to upgrading software, particularly the MS Office suite and drafting software like AutoCAD - I have a client reluctantly making the upgrade from Office '03 to '07 - to a person the office staff bitched and complained because they didn't like the transition from text-driven menus to Tabs...I have been teaching classes in '07 versions of Excel and Access to a group that doesn't want to learn it...lol. The engineers are worse though, running a 2000 version of AutoCAD Lite - when their systems were upgraded (to 7) and the version they were comfortable with was no longer an option (the 2000 version won't run on 7) - 3 quit rather than learn a newer version.
Moral of the story, people are often stupidly resistant to change, and these legacy OS systems aren't going anywhere any time soon.