Rather than slurping in the entire file before writing it out, it might be better to read in blocks of 4Kb (or some amount suited to your OS):

$/ = \ 4096; # read in 4Kb blocks

foreach my $file (@filenames) {
    open (INFILE, "$file") || die ("Can't open file $file$!");
    while( <INFILE> ) {
        print OUTFILE1;
    }
}

[download]
And if you don't really care about files that don't exist (i.e. just ignore them) you can simplify, simplify, albeit by introducing a trick with @ARGV magic: 
{
    local @ARGV = @filenames;
    while( <> ) {
        print OUTFILE1;
    }
}

[download]

<pendantry> ... and the correct term is concatenating (although some argue that it is catenating), rather than replicating. </pendantry>

In reply to Re: Replicate file (through concatenation) by grinder
in thread Replicate file by Anonymous Monk

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.