In general, it's probably a really bad idea to do this. Another programmer coming along reading your code (or you a few months down the line) expect the built-ins to do what they're documented to do. If they see something like: 
my $chomped = chomp (@array)

[download]
They will expect $chomped to contain the number of elements chomped as documented, not the first element of the array post-chomping. So unless you want to maintain a list of all the built-ins you've over-ridden at the top of your code and have any future programmers working on the code referring back to it constantly, you're better off just writing your own function. The two examples you give are trivially written as 
sub chomp_and_return {
    chomp @_; return @_;
}

sub lc_array {
    map { lc } @_;
}

[download]
which are just as easy to use as the built-ins, but give different names to different behavior and are consequently much more obvious to the reader.

If after reading and considering this post you still want to over-ride the built-ins with different behavior, see the "Overriding Built-in Functions" heading of perlsub.

In reply to Re: modifying perl functions without having to write own functions... by dirving
in thread modifying perl functions without having to write own functions... by argv

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.