In short - yes it is possible if you can connect directly to the recipients SMTP server. For the reasons "Rup" outlines it may not be especially practical, and if you are on a network behind a firewall you may not be able to get a connection to a remote server on tcp port 25 at all.
Assuming this doesn't apply for you, then here is the detail:
When you (as a mail client) log into the recipient's mail server, all that server cares about (for delivery purposes) are the recipients specified in
RCPT TO:. See RFC2821 - Simple Mail Transfer Protocol. It doesn't differentiate between the type of recipient (to:, cc: or bcc:), it just knows you are saying "make sure the recipient on your server receives this".
However, as far as the recipients actual mail client is concerned, it is the headers in the message that say who all the recipients of the message were. See RFC2822 - Internet Message Format.
In other words, the TO:, CC: and BCC: headers are there for the benefit of the mail client, whereas the actual distribution is handled during the SMTP 'conversation' with the mail servers.
So you can, in fact, have a conversation with an SMTP server that looks something like this:
C:>telnet aspmx.l.google.com 25
220 mx.google.com ESMTP f70si17620845wej.110
250 mx.google.com at your service
MAIL FROM: <email@example.com>
250 2.1.0 OK f70si17620845wej.110
RCPT TO: <firstname.lastname@example.org>
250 2.1.5 OK f70si17620845wej.110
354 Go ahead f70si17620845wej.110
cc: email@example.com, firstname.lastname@example.org
Subject: My email
Hi - this is a test
250 2.0.0 OK 1277401976 f70si17620845wej.110
221 2.0.0 closing connection f70si17620845wej.110
Connection to host lost.
The net effect is that
email@example.com receives a copy of the email that has him on the cc list as well as the original addressee
firstname.lastname@example.org, and the original cc recipient
However, since we never actually connected to the latter two's mail server, they don't actually receive the email second time around.