Because of this, I actually set up a pattern inside the interface description that includes the ip address. The physical interface gets one description, typically a circuit ID or some other information regarding the physical link. The logical unit gets a different description that starts with "ip/mask; ".
One side benefit is that "show interface descriptions" only displays interfaces that have descriptions. If you leave unused interfaces without a description, they are automatically filtered out without any additional work on your part.
Here's an example of what I do:
{master}
cmyers@lab-ex8208-1.re0> show interfaces descriptions
Interface Admin Link Description
ge-0/0/0 up up v2148 access ports
ge-0/0/3 up up v2150 access ports
ge-1/0/1 up up ESX server
ge-2/0/0 up up lab-mgmt-sw port ge-0/0/8
xe-3/0/0 up up LAG ae0: To lab-ex8208-2 xe-3/0/0
xe-3/0/1 up up LAG ae1: To lab-mx960-1 xe-1/2/0
xe-3/0/2 up up Ixia 5:13
ae0 up up XLINK: 2x10G link to lab-ex8208-2
ae1 up up UPLINK: 2x10G link to lab-mx960-1
ae1.0 up up 172.17.254.6/30; Routing link to lab-mx960-1
me0 up up 192.168.255.12/24; initial address for config
vlan.2148 up up 172.17.148.252/24; FX segment
vlan.2150 up up 172.17.150.252/24
vlan.2151 up up 172.17.151.252/24; MM segment
vlan.254 up up 192.168.254.12/24; in-band management link
The "v2148 access ports" and "v2150 acess ports" descriptions are just placeholders that I have set by default in the interface-range. In production environments those are actually the server names.
Cheers!
-Chad