That is, if you're willing to run another VNC server! If you run a VNC server in the guest you can connect with your vncviewer in full screen mode to that server. You end up running two VNC servers for each guest, one in the host to contain the VMware session, and one in the guest to handle your full screen access. More overhead obviously, but if you have cycles to burn and full screen is a big deal...
My own experience is this is worth doing if you can afford it. Mouse operation in particular in much smoother under the guest vncserver than under the host vncserver/VMware session.
Setup for the above in a linux guest is easy as falling off a log so I won't even discuss it.
In a windows guest there are a few setup gotchas.
The windows vncserver has to share the desktop with all other users. That means its geometry is the same as the root (in our case the guest window in VMware in the host VNC server). So you need to setup your host VNC session big enough to hold the full screen, plus the VMware junk, so that the windows root that the guest resident vncserver will see is the real screen size. For example: suppose your real screen is 1024x768 and your VMware window wrapper takes 60 pixels over and under plus 10 pixels on each side; use -geometry 1044x828 on the host resident vncserver so the VMware guest can see a 1024x768 screen.
If you want your wallpaper to show up you have to add the RemoveWallpaper dword tag to the registry as per the VNC documentation.