Hi,
thanks for the report. I will try to investigate this issue more thoroughly.
What I want to say now is, that the connections are definitely NOT in the LISTENING state. This is pure nonsense. Most probably your port monitoring tool is not working properly.
The connection either has some relationship with remote IP address, then it is connected (ESTABLISHED) in the process of connecting or in the process of closing (FIN_WAIT, CLOSE_WAIT, TIME_WAIT, etc.).
Or the connections is closed, without any relationship with remote peers, then it might be in a LISTENING state, waiting for now connection to be created on the port it is listening at. (also referred to as "opened port") THIS IS NOT THE CASE HERE.
WebShield surely listens on TCP port 12080, so that it can accept connections. It does that during startup and only listens on localhost:12080. During the lifetime of the connection, it does not change from ordinary connection, to the unconnected listening port - it is not even a supported operation, to listen on connected sockets.
I am not saying, that you don't have the connections opened, but they are not in the LISTENING state. It would be somewhat interresting to know what is their actual state. I suggest trying some other utility, either excellent "TcpView" from Microsoft (now), or the "Current Ports" app alanrf has mentioned, which I saw many people here using.
Thanks.
Lukas