This is expected behavior, so there is not really a “solution”. You can try to repackage the app with a policy, and not include the daemon, but the app likely won't work correctly.

As far as deleting the plist, you would also need to boot out the daemon or reboot the system to clear it as a running process.

Yeah, like previously stated, the only real options would be to delete the plists and bootout the daemon. You could do a post install script for this, but it might still launch briefly before that script kicks in. I agree about this being annoying behavior, but it is functioning as TeamViewer intended. You might be able to modify the installer package in Composer and create a new one without the launch plists, but that would create a lot more manual work for you every time you want to update TeamViewer as opposed to the simplicity of the AppCatalog deployments.