Here's a copy of the email I sent describing the issue:

As you may know, VRC 1.2 is currently in development, and it includes a feature
that allows a controller to provide a voice ATIS. It uses the VVL
FileBasedRecorder to create a recording, then connects it to a voice room, and
loops the transmission. The Voice ATIS exists as a second ATC connection to the
network, with a zero vis range, and a radio range equivalent to TWR connections.
The user can specify the voice server that the voice ATIS resides on. The voice
channel is hardcoded to match the ICAO code of the aiport, with an _ATIS suffix,
such as KBOS_ATIS. I've modified the FSD to return a Y for the CQ:ATC query for
_ATIS connections, so that they show up in the controller list within pilot clients.

Now for the strange issue: When I tested this out, I joined the network via SB3
and positioned my plane at Boston. One of the VRC testers (Paul Byrne) was
providing an ATIS as KBOS_ATIS on 135.000. He was also running TWR as BOS_TWR on
128.800.

When I first connected, the first thing I did was tune 135.000 (the ATIS freq)
in COM1. I immediately began hearing the voice ATIS as I expected. I then
pressed the COM1 standby freq swap button in order to detune 135.000. I had
122.950 in the standby position. So now 122.950 is my active COM1 freq, and
135.000 is in the standby slot. The voice ATIS stopped playing as expected.

I then decided I wanted to see what the KBOS_ATIS *TEXT* ATIS looked like, so I
clicked on KBOS_ATIS in the SB3 controller list, and chose "View Controller
Info". The text ATIS showed up in the SB3 window as expected, but unexpectedly,
SB3 connected me to the KBOS_ATIS voice channel and I began to hear the looped
recording again. Note that my COM1 radio is still tuned to 122.950, and not 135.000.

At this point I wasn't sure how to get the voice ATIS to stop playing. I hit the
COM1 frequency swap button, to tune to 135.000, which immediately disconnected
and reconnected the voice ATIS URL. I then hit the frequency swap button again,
to tune back to 122.950, and the voice ATIS disconnected. I then fetched the
text info again for KBOS_ATIS, and the problem repeated ... it reconnected me to
the voice ATIS channel without me tuning 135.000.

In order to narrow it down a bit more, I did the following:

After tuning 135.000 and then back to 122.950 in order to stop the voice ATIS
from playing, I then tuned 128.800 on COM1 in order to connect to BOS_TWR's
normal control voice channel. I then clicked on KBOS_ATIS and requested the text
ATIS. This time, SB3 did *not* tune the KBOS_ATIS voice channel ... it kept me
on the BOS_TWR channel. So this bug(?) only occurs if you are not already
connected to a voice channel, apparently.