Presently IPv6 only works on the LAN side. Disabling IPv6 is a waste of time and most often it only causes problems. The few sites you can access with IPv6 are only for testing purposes only. The Op is worried about a problem that simply does not exist, been here done this already a few times in fact.
Read more about this below.
I know what it's for and the reason for using it, but when it actually will be used on the WAN in place of IPv4 is another question entirely. The reason for doing this is because IPv4 is limited on address space where IPv6 has much greater address space.
From Wiki:
Larger address space
The most important feature of IPv6 is a much larger address space than that of IPv4: addresses in IPv6 are 128 bits long, compared to 32-bit addresses in IPv4.
[1]


Decomposition of an IPv6 address into its binary form
The very large IPv6 address space supports a total of 2
128 (about 3.4×10
38) addresses—or approximately 5×10
28 (roughly 2
95) addresses for each of the roughly 6.8 billion (6.8×10
9) people alive in 2010.
[12] In another perspective, this is the same number of IP addresses per person as the number of atoms in a metric ton of carbon.
The Argument against Disabling IPv6
It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.
Read more.
http://technet.microsoft.com/en-us/m....cableguy.aspx