It's not a bug. I'm pretty sure it has to do with something about magazines must have an owner. Remote communities aren't "created" on the local instance but instead "synced up" and so it uses the admin account as the owner of the newly created magazine.
Remote magazines can be created on the local instance even without someone explicitly searching for it (I believe since that what seems to have happened on my instance) so I believe it just assigns the owner to the admin.