There was a good post about this in the AOPA forums recently. Read this if you have access:
http://forums.aopa.org/showthread.php?t=39537
If you can't access the above forum, I'll try and summarize...
If you don't, the AOPA thread was a rehash of this one:
http://www.purpleboard.net/~purplebo/forums/showthread.php?t=2700
Although they diverge a bit with some info being posted on one and not the other.
The bottom line is that these are two completely separate ILS systems. If you check throughout the US, you'll see that there are just so many ILS frequencies - the same ILS frequency is used in many places - the only thing unusual with this situation is that they are at the same airport.
In normal (ILS in use for approaches) it should not be an issue. If ATIS is reporting "ILS 21 in use" for example, ATC has flipped the switch to bring the right one online. There's not a lot of material on this from the FAA; AFAIK it's not even discussed in the AIM, IFH or IPH. All I've ever come across are the two blurbs from the ATC handbook that are quoted in the two threads:
==============================
4-7-10.d. Advise pilots when the ILS/MLS on the runway in use is not operational if that
ILS/MLS is on the same frequency as an operational ILS/MLS serving another runway.
==============================
and
==============================
4-7-13. SWITCHING ILS/MLS RUNWAYS
TERMINAL
When a change is made from one ILS to another or from one MLS to another at airports equipped with
multiple systems which are not used simultaneously, coordinate with the facilities which use the fixes formed by reference to these NAVAIDs.
==============================
But you will notice from the charts that the identifiers of the two localizers are different - so the rule that we both tune =and= identify has special meaning.
BTW, another of these is at KFTG, just east of KDEN, where the ILS 17 and 35 share the same frequency.