Networking Issue with Thunderbolt Display's Ethernet Port

My Problem and a wall of TL;DR geek speak.

Hello all and thanks in advance for your help. I have a Late 2011 MacBook Pro 15 (8.2) running OSX 10.9.3 hooked up to a 27' Thunderbolt Display and I am really tired of manually disabling, reenabling and managing the switch between WiFi and the display's ethernet port. When I am away from my desk I'm typically making use of the WiFi as most people do but when I'm back at my desk the display is hard wired into my home network (as is likely the case for many many users of a similar setup).

The issue is that contrary to what the consensus appears to agree about on the internet my device will not simultaneously use both connections. When WiFi is connected the display will get a self assigned IP address. I then am forced to manually turn off WiFI and release and renew the DEP's IP settings. (Display Ethernet Port)

This is likely due to the fact that my DNS server is assigning static IP's via MAC address as opposed to automatically assigning them to any authenticated request. I won't go into detail about the reasons for that unless someone finds it prudent to the issue.

I've had some issues coming up with a workable resolution to this issue and I'm hoping that one of you will have come up with a clever solution to this.

Steps I've Taken to Resolve The Issue

- I've made sure that the Network Connection Priorities are set correctly.

The DEP is the highest entry and thus first choice in my network connectons list.

- I've attempted to bypass DHCP all together and manually assign the correct IP to the interface.

This works and actually allows both devices to be connected, unfortunately it assigns to the same IP to both interfaces and this is causing IP conflicts when doing some things. This also forces me to manually update that entry if DNS ever fails to authorize an address renewal and the appropriate IP internally changes.

- I've written a simple bash script that automates the process when run.

This could potentially resolve the whole issue if someone is aware of a way to poll for the thunderbolt display connection event in bash or applescript. This would allow me to automatically execute this script when the device detects that the thunderbolt display has been plugged in.

Sad Pandas are Sad.

Well there you have it, I can only imagine that somewhere hidden away in the depths of the internet there's some prophetic sage who can help me figure out what I'm overlooking or doing wrong. I can't imagine I'm the only person in hte appleverse that has run into this issue.

Once again I really do appreciate your help and time.