I posted over on the MS Forums as well and basically got a "yep, this is how it...

We're using an OLEDB Command task to execute the stored procedure, and I believe that treats it as dynamic SQL and executes that new system sproc as part of validation...

Collation is SQL_Latin1_General_CP1_CI_AS returned from that query...

I suspect it would be easy for anyone to reproduce unless something in our setup is weird.

Here's a quick script...

create proc test @test1 varchar(128)...