Yeah, there's next to no need to go out of your way to support 64-bit on Windows if the program doesn't specifically require it (which is the vast bulk of consumer software) because 32- and 64-bit interoperability is virtually transparent and handled almost completely without user interaction. Mac OS X is better in some ways since you don't have to worry about drivers (on genuine Apple hardware anyway), 16-bit software or 32/64-bit separation of certain system directories.
Linux, on the other hand, is a completely different animal. multilib is OK, better than having to maintain a 32-bit chroot, but it lacks the transparency offered by Windows or Mac OS X. It's next to useless for pre-packaged software since package managers will reject (quite correctly, though for the wrong reasons) anything not in the same binary format as the system. More annoyingly, if you have a 32-bit app that requires a library not offered in your distros pre-packaged collection of 32-bit libs (such as FSO and libogg on amd64 Ubuntu), then acquiring and adding it to multilib requires more effort and skills than should be required for a desktop OS.