You should create a sub-routine that handles these for you. For example: 
sub mprint
{
        my @fh;
        push(@fh, shift) while (ref($_[0]) eq 'GLOB');

        print $_ @_ foreach (@fh);
}

open($so, ">&STDOUT");
open($se, ">&STDERR");

mprint $se, $so, "This tests\n";

[download]
It's not quite as clean as the builtin, but it's pretty close. You could even group your filehandles together into array packages, so that it's tidier: 
my @default = ($so);
my @log_and_print = ($log, $so);

mprint @default, "Standard message\n";
mprint @log_and_print, "This goes to log and screen\n";

[download]
Update:
IO::Tee looks like a great way to do this as well, provided you can install your own modules.

In reply to Re: Printing to multiple file handles with one request by tadman
in thread Printing to multiple file handles with one request by gnu@perl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.