I can confirm this in PowerShell and bash. When you re-deploy with the --copy --force command you get an error "A resource must be a file, an empty folder or a symlink".
I did a little debugging and found that the doRemoveFolderRecursively method is calling the RecursiveDirectoryIterator. When the files are iterated through, the dot symlinks are being passed through to doRemoveResource and if the current folder has files in it that error will be thrown.