Yes and no. ZFS snapshots can live for YEARS without problems.
VMWare snapshots, (and Linux LVM snapshots), appear to be some type of transaction log, which accumulates all the writes while the main storage is read only. This means the longer it lives, and more data written, the longer it takes to remove. This seems to be due to applying all the changes back to main storage, which I've seen in production take hours. And if the VMWare snapshot accumulated a huge number of changes, absolutely KILL performance, (because of all the disk I/O).
To be fair and clear, destroying a ZFS large or huge snapshot can take a long time too. But, an extremely early feature added to OpenZFS, (but not to Sun / Oracle ZFS until years later), was asynchronous destroy. This means destroying a large or huge ZFS snapshot, (or dataset), might take hours, even days. But, it's done in the background with full pool access, (though a little slower due to all the disk work). The formerly used space becomes incrementally available as it's freed. You can even export the pool or reboot without problems. This async destroy continues where it left off without issue. ZFS will even tell you how much still needs to be "freed".
A new feature probably not yet added to OpenZFS, (and might not ever be), is an asynchronous delete. Deleting large or huge files can take time. There is a thought that OpenZFS could use the same method as async destroy, but for deleted files that are large or huge. The exact size between immediate delete, and async delete seemed to be tunable.