As far as I get it, you want to simulate your bridge having another port, but you don't want any real hardware. Though it sounds pointless to me, here are some options:
1.) You may think you need an additional interface, but really just need an additional IP address. If this is the case, just assign it to the bridge (any interface can have multiple IP addresses). Example: "ip addr add 192.168.72.4/24 dev br0". Note that ifconfig will only show one address - to see all assigned addresses, use "ip addr show".
2.) Run a virtual machine on your system and make it appear that it's network card is connected to the bridge. Make sure not to use NAT networking for the VM - instead use TAP, or, with VirtualBox, "host-only" networking. Then, on the host, add the guest interface into the bridge.
3.) Make two TAP devices (tap0, tap1). Add tap0 to the bridge. Start some program(s) to join the software ends of tap0 and tap1 into each other. Then it will be as if tap1 is connected into the bridge with a cable - you can assign it an IP address etc.. (but DON'T assign an IP to tap0).
For example, with my open source VPN software (
http://code.google.com/p/badvpn/ ):
First configure the TAP devices.
root # openvpn --mktun --dev tap0 --user myuser
root # openvpn --mktun --dev tap1 --user myuser
root # ifconfig tap0 up
root # ifconfig tap1 up
Then run the following daemons, which will make it appear as if tap0 and tap1 are joined into each other (it will be identical as if you had eth0 and eth1, and connected them directly with a cable).
myuser $ badvpn-server --listen-addr 127.0.0.1:7000
myuser $ badvpn-client --server-addr 127.0.0.1:7000 --transport-mode tcp --bind-addr 127.0.0.1:7001 --ext-addr 127.0.0.1:7001 local --tapdev tap0
myuser $ badvpn-client --server-addr 127.0.0.1:7000 --transport-mode tcp --scope local --tapdev tap1