Pawan -
I don't have jQuery integrated, but it looks like based on the response from the 'alert' that the code you provided will return the ID I need, so I marked yours as an awnser.
I came up with another soltuion as well. I ended up passing the exact controlID (UniqueID), the one that initiated the doPostBack, as the 2nd parameted provided to the originating doPostBack call since I was previously passing it nothing (''). Then that parameter/eventarg was extracted as follows and shown above:
document.forms[0].__EVENTARGUMENT.value
So basically the originating doPostBack call is passed the same ID for both the 1st and 2nd parameter. While this works well for me, because I can get the 2nd parameter containing the raw UniqueID param passed in, it may not work for others who are already using the 2nd parameter of the doPostBack call to pass some other value. The solution would be to pass an array of values to that 2nd parameter and know which one was the original control ID to extract out, or to use the jQuery solution from above.
One important note about this thread too, the reason I need to use 'UniqueID' when calling the doPostBack call is because I have a master page and a content page. Using the ConrtolID of a control to trigger a doPostBack on a content page does not work, and the UniqueID must be used. Had this been a regular .aspx page, the original code I used would have worked perfectly with no modifications or preservation of the originating control ID needed.