using sh() vs. execute() in a Jenkins Groovy shared library design - switches between hosts?

Question

When using a piece of test code running \'sh\' vs \'execute\' i noticed a great differences in environment variables. It quickly looked as if two totally different host were inv