I basically agree with user225005 -- the Windows limitation is, in a technical sense, in its boot loader; the BIOS-mode boot loader requires the use of MBR, and Microsoft has decided (for whatever business reason) to not support GPT. In theory, somebody might be able to write a BIOS-mode boot loader for Windows that would support GPT, but I don't know how hard it would be in practice. (There may be things further up the stack that would flake out.)
Using a second drive, as user225005 suggested, is the simplest way to work around the problem. If that's impractical, you might look into using the Developer's UEFI Environment (DUET) or Clover. These are both EFI implementations that can be installed like a boot loader on a BIOS-based computer. DUET is intended for developers and is not easy to install, but the page to which I linked includes pointers that should help. Clover is a Hackintosh (OS X on standard PC) boot loader, which is easy to install from a Hackintosh environment, but there's no documentation about installing or using it without OS X. Both work well on many Intel-based systems, but they don't get along as well with AMD CPUs. FWIW, I'm booting a laptop via DUET, which works reasonably well -- but I wouldn't recommend that the average user set this up unless it's absolutely necessary.
Another option is to use a hybrid MBR. This is an ugly and dangerous hack that enables Linux to see the whole disk via GPT and Windows to see up to three partitions via a modified MBR. Macs rely on hybrid MBRs when dual-booting with Windows, and you could do the same for a Linux/Windows dual-boot. As detailed on the page to which I linked, though, hybrid MBRs are very flaky, and a mistake when using them (such as using a Windows partitioning tool to modify your partitions) can lead to disaster. If it's a choice between the two, I'd recommend you try DUET or Clover first, and then fall back on a hybrid MBR only if you can't get DUET or Clover to work.