You could just use scp. scp is way better than sftp for scripting, IMO. And also, for sysadmin type tasks, I would rather use Perl as glue, than try to reinvent tools with it just to do it in Pure Perl. Just too... religious, for me.

I use public/private keys for authentication in this case, because not only is it (only slighter) safer than putting the password in the script, but it removes the need to interact with scp in order to transfer files.

perl -e '@hosts = ( map { $_ . q[.example.com] } qw/ foo bar www / ); 
+system( q[scp], q[-r], @ARGV, sprintf(q[%s:remotedir], $_) ) foreach 
+@hosts;' /tmp/foo
[download]

Here is another version using ssh and rsync, so as to only send the parts that changed, and ignores .CVS files:

perl -e '@hosts = ( map { $_ . q[.example.com] } qw/ foo bar www / ); 
+system( q[rsync], q[-rcC], q[-e], q[ssh], @ARGV, sprintf(q[%s:remoted
+ir], $_) ) foreach @hosts;' /tmp/foo
[download]

Of course, if the usernames on the aren't the same, you have to add that also.