I had to check this before I chimed in, but have different monitors (27" Acer 1920x1080, and old Gateway 21" 1680x1050) and can open multiple VST3s on the Gateway. I use "Extended" for Display mode when I enable the second monitor, and I started throwing VST3s on tracks (they actually open with the left edge on the second monitor anyway) until I got it too cluttered. No issues with this (I did not use the multi-dock).
 
What video card, monitors, and "violating VST3s" is the OP using?
 
 

I haven't had any problem putting VST3s or any plugins with CV  and not CV.on my second monitor. I don't use the multidock for that. 

nVidia Geoforce GTX 470 using the dual DVI outputs...SamSung Sync Master @1680 x 1050 primary Westinghouse L1928NV @ 1280 x 1024 as secondary...I have turned off all nvidia extra services (*but want to keep the streamer service going because I unload some of my vst's onto the gpu via Cuda Cores) in checking though I did disable all services proggys other than basic drivers...
 
The vst's can remain pinned if I X out of the console view in second monitor but it sort of defeats the purpose, maybe I am missing the point of the pin function, I was under the impression that pinning something kept it "on top" of the video window, which is not the case in this scenario...however it IS the case in the primary monitor...
 
Frankly it's an eye candy issue for me, I can work around it and do, but it does suggest a bug of sorts because the behavior is not consistent between the monitors.
 
Running 64 Win 7 (sp1), 64 Sonar, Amd Phenom II x6 1090T 3.2 Ghz w/16 GB ram
 
*Nebula and Liquid Sonics both have vst2's that allow me to offload to the Cuda bridge (which I disabled to test configuration) and use parallel processing on my cuda cores to handle heavy programs, I generally only use it on cpu intensive emulations.

Hi.
There is already filed a problem report on the saturation knob issue. I had this on X3e x64 as well as on SPLAT x64 (incl. update). I am getting more and more convinced that this is a bug, and not a settings issue. Had a teamviewer session with a cool representative from Cakewalk, and he found no problems with my settings (Win7 x64, or SONAR X3e) or my installations (DAW and plugs). This is a dedicated Studio pc, with nothing more than audio related software (DAW and plugins).
I am using Win7 x64 on a 2,5 GHz Quadcore intel, Sapphire Radeon (512 Mb, dual 24" monitors, with screen resolution1920 x 1080), Echo Audiofire 8, and a Novation Nucturn. x 

It could be that things work fine if the second monitor is on the right, but fail if the second monitor is to the left. This is because when the second monitor is to the left, all X coordinates on it are negative. These are valid coordinates, but some applications do silly things like check if a coordinate is negative and fail in some way, or range-limit coordinates from 0 to some positive value, causing things to break. Temporarily re-arrange your monitors in Control Panel > Display > Screen Resolution so that the second monitor is to the right, and see if the problem persists.

My secondary is above my primary...so no...I've changed resolutions and configs...its a bug

Psychobillybob
My secondary is above my primary...so no...I've changed resolutions and configs...its a bug

That would mean negative Y coordinates, so that same issue can apply. You can test this by temporarily moving it to the right or the bottom.
 
Yes it is a bug for sure, just trying to narrow it down a bit and see why only some people experience the issue.

My second monitor is to the left as well, but I admit that I have never used the "pin function" once. I also do not often dock a VST, so leave the UIs open on the second monitor in a floating fashion. The most common use of how I use this is two instances of Voxengo's SPAN before and after an EQ insert.
 
Just because others cannot replicate an issue does not invalidate that the OP is seeing it. It is definitely worth taking the time to submit a problem report on this if desired.

Thanks for the thoughts and suggestions, I have changed my primary/secondary monitors and reversed them (using the smaller monitor as primary) also reset resolutions until both were using the same (defaulting to the smaller monitors settings) in ALL instances the Saturation knob is the ONLY PC module that has issues and the pin function does not remain on top of the window in second monitor...so yeah it's a bug...if I could get it to work by downsizing my resolutions I could live with it being some kind of video flux but since the saturation module shows up blank and does not respond to user controls (and is the only one doing it) and the vst's remain pinned in the primary monitor I am going to stick to my own observations that it's a code issue...again I am not big into eye candy so the visual falls well below the thresh hold of priority for me, but since it is a code issue (in my opinion) the issue comes down to user control NOT producing the desired outcome via code control...as always your mileage may vary.

I have three monitors.  My TV is on the big LED television screen (at a lower resolution) on the wall and the CV is floating and stretched over two 22" monitors.  If I try to pin plugins over the CV they will end up under the CV and I have to move the CV to get to them again.  Like the OP, if I keep the plugins over the TV on the big screen, the plugins remain on top.
 
It would be nice to get this addressed.
 
EDIT: FWIW, it doesn't matter if the plug is VST2 or VST3.