Transfer SQL Server Objects Task - Why does it try to drop logins

My ultimate goal is to use the Transfer SQL Server Objects Task to copy
schemas only (no data) all the objects (tables, procedures, views, etc.) from
a very large (100 GB+) database to another database for the purpose of log
shipping this small database to a disaster recovery site. I actually plan to
also copy small lookup tables in the smaller database. That's my goal, but
I'm taking little steps first by using a test database with one small table
to copy to another empty test database.

Now....the problem. In the task editor, I enabled the following properties:
DropObjectsFirst
IncludeExtendedProperties
CopySchema
IncludeDependentObjects
CopyAllObjects
CopyTiggers
CopyPrimaryKeys
CopyForeignKeys
CopyData - False ( I don't want to move data, just empty objects)

This is a bit of overkill for my little test database with one table having
10 rows, but more aligned with my ultimate goal. So far so good.

When I run this, I receive the following error:

SSIS package "Package.dtsx" starting.
Error: 0xC002F325 at Copy Test, Transfer SQL Server Objects Task: Execution
failed with the following error: "ERROR : errorCode=-1073548784
description=Executing the query "IF EXISTS (SELECT * FROM
sys.server_principals WHERE name = N'fakelogin')
DROP LOGIN [fakelogin]
" failed with the following error: "Could not drop login 'GLADCTEL' as the
user is currently logged in.".

The "fakelogin" above doesn't even have access to this test database. Why
would SSIS try to drop this login, or any login for that matter? I would
like to copy users, roles, and permissions eventually, but I did not enable
these options yet.

I've Googled but can't spot this exact problem. I saw plenty of other
problems about this task though, and they don't leave me feeling warm and
fuzzy about this task.

Thanks in advance for any help.